Connect to a server

Before you can work in XECUTE, you need to connect to a server and open a scenario. A scenario is a saved version of the mine plan within an environment.

XECUTE is an enterprise application that runs in a live environment, which means:

• All data is stored on a central server (not your local machine).

• Multiple users can work on the same plan at the same time.

• Real-time updates flow in from operational systems (via Data Feed In), and outputs are published automatically to downstream systems (via Data Feed Out).

Systems overview

Connecting to a server relies on two main components:

• EPF (Enterprise Planning Framework): RPMGlobal’s enterprise platform that manages authentication, security, and data exchange between applications. Within EPF, the OMI service acts as the gateway for XECUTE to connect and authenticate.

• XECUTE Server Manager: This tool is used by administrators to configure XECUTE environments, databases, and services.

Technical details

This page details connecting to a server within XECUTE. For information about setting up and managing servers, refer to:

• XECUTE Admin Guide

• EPF Admin Guide

• Web Deployment Admin Guide

Terminology

• Connection profile: A saved set of details that tells XECUTE how to connect to the EPF OMI server (host name, port, protocol, authentication).

  • EPF (Enterprise Planning Framework) is RPMGlobal’s enterprise platform that provides authentication, security, and data exchange between planning applications, providing structured data flow and integration across mine planning systems.

  • OMI refers to a service layer within EPF that XECUTE uses to communicate with the services. It handles things like authentication, connection management, and data exchange between XECUTE and EPF services.

• Environment: A specific XECUTE instance within the server (e.g., Dev, QA, Production). Each environment has its own scenarios and data.

• Scenario: A working plan within an environment.

Before you start

Make sure:

• XECUTE Client and Config are installed.

• You have the EPF OMI server address.

• You know which authentication method to use (Windows, Microsoft Entra ID OAuth2, Client Certification).

Connect to a server

When you launch Client or Config, the application uses a connection profile to link to the XECUTE service on your company’s server.

• If XECUTE was installed using a WebDeploy (web deployment) portal, the connection profile is already set up. In this case, you don’t need to manually connect to an installer.

• If it was installed offline, you need to create a profile by entering the server address and authentication details.

The connection ensures you’re working in the live environment where all data, updates, and outputs are synchronised. Without this, you can’t access scenarios or publish schedules.

To check or set up a connection, click the Service Connection icon in the top-right corner.

Installing from a web deployment page

To install XECUTE from a web deployment page, automatically connecting to the server, browse to the XECUTE server name in your browser – then click the Config and Client tiles to open them.

While web deployment automatically installs XECUTE, the page includes links to offline *.msix installers in case you need them. If you need offline *.exe installers, contact RPM Support. Note that *.exe installers require administrative privileges to install.

Manage service connections (manually connect)

To manage connections manually (add, edit, or remove), open Client or Config, then click Manage Service Connections on the title bar.

Select an environment

On the Service Selection dialog, select the environment you want to work with.

If no environments are listed, click Profiles to manage connection profiles.

Select a service profile

On the Service Connection dialog, select the server profile you want to work with.

If no server profiles are listed, click Profile to manage profiles.

Manage service profiles

The dialog lists the service profiles you’ve connected to.

To add a service profile, click Add.

Add service profiles

Add Service Profile
Profile Name	A unique name for this profile (e.g., Production, QA, Training)
Address
Protocol	Select HTTP for a standard connection or HTTPS for a secure, encrypted connection. Use HTTPS if your IT team has configured the server with SSL/TLS certificates
Port	The port number for the EPF OMI service. Defaults: 6401 (HTTP) or 6400 (HTTPS).
URL	The full URL of the EPF OMI service, including protocol and port. Example: https://epf.company.com:6400/ProcessRequest.
Authentication
Type	Select how you’ll log in: Windows: Uses your Windows Active Directory credentials. Can be used if the EPF OMI server and your computer are on the same domain, or if there is a trust relationship between the two domains when they are different. Microsoft Entra ID: For Single Sign-On (requires setup in EPF). This option requires setup by your system administrator. Microsoft Entra Domain Services must be configured in EPF using RPM Integration Management Studio before you can use this method. User Credentials (OAuth 2): Prompts for username and password. Used when you're outside the domain or need to log in as a different user. Username/Password: Prompts for username and password using basic authentication. Not supported. Client Certificate: Uses a signed certificate from your Windows Certificate Store. Only available when using HTTPS. Require strong certificate-based authentication. Certificate must be installed and HTTPS must be configured on the server.
Certificate	Uses a signed certificate for authentication. Choose the certificate from the list of certificates installed in your Windows Certificate Store.
Timeout override (s)	Select to adjust the timeout in seconds when connecting to the EPF server. If a connection isn’t established within the timeout, an error message is shown. The default timeout is 60 seconds.